Looks like I'm doing something wrong but I'm a little lost at what the travis-ci/pr test is doing.

The mocha test run fine before the error line.

I'm trying to find out how to reproduce the problems locally, but I can't replicate it, instead I get a tonne of errors from eslint (Around 82 Errors, largely deprecation notices).

The additional tests are great!

I just did a clean checkout of master, ran npm install, and then was able to successfully run both gulp test and gulp lint without any issues. I'm not sure why you ended up needing to include various linting changes in this PR, but they don't appear necessary to me. Can you try again with a clean checkout/npm install and see if you run into whatever problems you faced initially related to linting?

If you do see issues with our linting setup, let's address it in a separate PR, ideally one that also involves moving to the new Google-specific eslint config. See #66

I think it would be ideal to just limit this PR to the new tests.

Will address in seperate PR's.

The linting caused issues in travis and when I ran it locally the linting through up way to many warnings for my liking.